2012-09-27 - 4674.700 - Spec - BW Performance (Contract Infocube) #SalesDistribution
SPECIFICATIONS
4674.700 - BW Performance (Contract InfoCube)
Requirement Summary
Create a Info Cube in BW to store the Contracts and its related call offs for reporting on Open Contracts in NEC.
Admin Info
| Purpose |
BW Performance (Contract InfoCube) |
| Requested By |
Mark Harris |
| Spec Created By |
Chandramouli K |
| Spec Created Date |
02/11/2013 |
| Spec QA by |
Uday Kumar P |
| Objects |
ZSD_CONTR - Contract order Info Cube |
| Document Status |
Complete |
Prior Tickets
2247.200 - Create a new report for Contract Orders
Documents
Contract_Fields_12-14-2012.xls
Contract Requirement_12-14-2012.doc
Contract_Fields_01-25-2013.xls
Functional Requirement
12-14-2012 - Email from Ashwin - NEC requested us to show Contract Orders and it's Call off's as per OSA600 Report seen below:
01-11-2013 - Call with Ashwin - NEC Requested us to make following changes and send the list of fields in the Contract InfoCube:
1. Calculated the Open Ref Qty for a contract in InfoCube.
2. Include Contracts as well as Call Offs related to that contract.
3. Include Quantity Key Figures in Eaches.
4. Perform Fiscal Year calculation based on current year for contracts.
5. Bring Only Open Contracts into the cube.
6. Include all the fields that are used in the Open Order cube.
01-23-2013 - Email from Ashwin - NEC Requested us to test the following scenarios for the Contract InfoCube:
Test Case 1: One Open Contract with multiple Open Call offs and with Open Contract qty.
Test Case 2: One Open Contract with multiple closed Call offs and with Open Contract qty.
Test Case 3: One Closed Contract with multiple Open Call offs with Contract Status Complete.
Test Case 4: One Closed Contract with multiple closed Call offs.
01-23-2013 - Call with Ashwin - NEC Requested us to test the following scenarios for the Contract InfoCube:
1. Exclude call offs for Closed Contract in Contract InfoCube.
2. Exclude Closed Contracts in Contract InfoCube.
3. Update only open contracts in Contract InfoCube
01-24-2013 - Call with Ashwin - NEC Requested us to test the following scenarios for the Contract InfoCube:
1. Exclude document types other than 'G'(Contracts).
2. Exclude document types other than 'C'(call offs for above contracts).
02-07-2013 - Call with Ashwin - NEC Requested us to test the following scenarios for the Contract InfoCube:
1. Include Logic for deleting the Contracts and its call offs, when contract cancel date is less than system date(SY-DATUM).
2. Add the contract Condition Data to Condition Cube(ZSD_C15).
Solution Summary
1. Need to create a New Contract Order Cube that should contain only Open Contracts and its related call off's from existing AFS Sales Orders ODS (ZAFSDDS1) that has all the Sales Orders information.
2. This solution should also meet the requirements for designing OSA600 report (the format displayed in the screenshot above).
3. Need to include this new Contract Cube in MultiProvider 'MP for Open Orders, Condition and Sales Analysis' (ZMP_OPASA), so that it can be used for diplaying the contract qty and value in EPM Scorecard reports.
Test Plan
| SNo |
Test Scenario |
Expected Results |
| 1 |
Contract cube should contain only the Contract Orders and its related call offs. |
Contract Cube should only have Orders with document category 'G' and its corresponding call offs with document category 'C'. |
| 2 |
Check the value of calculated Open Reference Quantity for a Contract. |
Open Reference Quantity of contract should be confirmed Contract quantity minus confirmed call off quantites of all its related call offs. |
Solution Details
1. For designing this requirement, we will require the following infoproviders:
a) AFS Sales Order DSO (ZAFSDDS1) that contains complete information about all types of Sales Orders.
b) Order Conditon data cube (ZSD_C15) that contains the condition informatiron for Open orders and contracts.
c) Multiprovider for Open Orders, Condition and Sales Analysis (ZMP_OPASA) that will combine the data from open orders and contract orders along with their conditon information.
d) Condition data DSO (ZSD_O05) that contains conditon information for all types of orders.
e) Finally the Contract Order cube (ZSD_CONTR) that needs to be designed to fulfill NEC requirement.
2. We need to load only Contract orders and its Call offs from AFS Sales Order DSO into Contract order cube. In this process, we also need to calculate the open reference quantity of contract orders as follows:
Open Reference Quantity of a Contract = Confirmed Contract quantity - Confirmed quantity of all call offs related to that contract.
3. Next we need to load data from Contract InfoCube to Condition Infocube and look up into the Condition data DSO to populate Condition key figures for Contracts.
4. Finally we have to include Contract Order cube and Order condition data cube in Multiprovider for consolidated reporting.
Issues
1. NEC wanted us to design Contract InfoCube with the same fields as in Open Order Cube. But due to functional constraints, we have to eliminate the time characterstics from Contract Order Cube except 0CALDAY.
2. While creating BEx Query on this Multiprovider to show Contract data along with other cubes data which exist in this Multiprovider, should not use filter restrictions on time characterstics. If filter restrictions are used, then itwont fetch data data from Contract Cube.
3. Faulty contract orders may display inconsistent results in the reports, that need to be handled at the report level.